Internet Surfer 2.0

home *** CD-ROM | disk | FTP | other *** search

/ Internet Surfer 2.0 / Internet Surfer 2.0 (Wayzata Technology) (1996).iso / pc / text / mac / faqs.350 < prev next >

Wrap

Text File | 1996-02-12 | 28KB | 679 lines

Frequently Asked Questions (FAQS);faqs.350 QUESTION: How do I compute the numbers for the video modes? ANSWER: See if there is an entry that matches your chip/monitor in XLIB/etc/modeDB.txt. Use the clock entries for your chip and the mode entry for that clock appropriate for your monitor. If you cant find a mode entry for a particular clock 'needed_clock' but can find a mode entry (for your monitor) for a nearby clock value 'found_clock', scale all numbers in the modeDB entry by (needed_clock/found_clock). man X386 and Read CONFIG and Xconfig.notes. QUESTION: How can I determine the clocks on the video chip? Where can I find clock.exe or clock.pas ? ANSWER: The XFREE Team discourages the use of clocks.exe and wants it to be removed from all docs, since the new Server is better at guessing the clocks than clocks.exe. You can get X to tell you what it finds by commenting the clocks entry in Xconfig. Use 'startx 2> x.err' to log the output. If X starts up this file gets the clocks only after you exit. I strongly advise using the 'modegen' spreadsheets to generate the appropriate settings. If I remember correctly you can find them in 'pub/linux/packages/SLS/x4' called modegen.taz or something equally as obvious ... Good luck. (Andy asb@cs.nott.ac.uk) The clocks entry in Xconfig serves as an index. example: clocks 1 2 ModeDB 1 640x480 ..... 2 800x600 ..... means the first clock on the chip will be used for the 640x480 mode and so on. Usually one uses the MHz value for the clock for convenience instead of 1 2 you probably have 25 28 ... etc. QUESTION: What are the settings used with a trident-8900C? ANSWER: To get X/SLS/Linux working with a trident-8900C, do the following: 1) From Frank Houston fh8n@uvacs.cs.Virginia.EDU vga256 Virtual 1024 768 ViewPort 0 0 Modes "1024x768" "800x600" "640x480" Use the VESA monitor timings from the modeDB in the example Xconfig. You do not need to specify the chipset or clocks. 2) From: Henk Vandecasteele henkv@cs.kuleuven.ac.be TRIDENT TVGA 8900C card with BIOS C2.11, A cheap color monitor AOC (CM-335) with a maximum horizontal frequence of 39.5 vga256 Virtual 1024 1024 ViewPort 0 0 Modes "912x684" "800x600" "640x480" # This mode drives my monitor to the limit (VESA timings for the rest). "912x684" 45 912 944 1104 1136 684 684 690 712 QUESTION: What are common problems with Xconfig? ANSWER:If X isn't firing at all, or even if it clears the screen and crashes (see below) you almost certainly have a fault in Xconfig. 1. Note that the server X interprets Xconfig. (not xinit) 2. If you have a fault in Xconfig it is possible to crash or hang the server without getting an error message. 3. leave the two paths at the top of Xconfig commented out when testing. 4. test with only one graphics mode included - one you are most sure of. 5. If you make a mistake in the mouse section, you will (I understand) get an error message, so if you don't get some mouse error, try elsewhere first. (eg "No such file or directory" indicates you have a fault in the "/dev/ttyxx" line, or /dev/ttyxx doesn't exist. 6. *NB* X looks in your home directory first to find an Xconfig. make certain it's using the one you've been working on! 7. you need double quotes (") around your chipset and modes: eg chipset "et4000" Modes "640x480" "640x480a" "800x600" and around the /dev/ttyxx eg.: microsoft "/dev/ttys1" 8. Check your VGA section and modeDB first. 9. ensure ModeDB clock speeds match the VGA section. Comment out any unused lines in MODEDB. eg clocks 25 36 00 00 00 00 00 00 then you *must* have (and only have) lines under modeDB corresponding to speeds 25 and 36. If you have one with (say) 62 uncommented out in the modeDB section in place of the 36 line, you will cause the server to die immediately with no error message. 10. a syntax error (such as an unrecognised word) in Xconfig will cause a death with no warning. 11. videoram must equal the amount of display ram on your chip. QUESTION: What do I use in my Xconfig file to use the bus mouse? Logitech doesn't work with my Logitech busmouse. ANSWER: (Nathan I. Laredo) Here are the mouse lines from my Xconfig: BusMouse "/dev/mouse" You may add a sample rate if you want, but chances are, unless the model number on your mouse matches mine: PC-93-9MD it probably will cause your machine to lock up, as I've gotten several reports saying that. According to the X386 documentation, non-logitech mice do not support a sample rate. XI.G X-APPLICATIONS: Compiling X Programs. ~~~~~~~~~~~~~~~~~~ QUESTION: Does anyone know where I can find the libobz.a library ? ANSWER: This library contained the socket stuff, when X386 V0.1 was released. Meanwhile it has found it's way into the kernel, so remove -lobz from the link step in the Makefile. QUESTION: I get _setjmp undefined when linking xv from .a files. ANSWER: You are trying to link a program compiled with gcc-2.2.2 and setjmp has changed sice then. Recompile xv from the source using the latest gcc. QUESTION: How do I compile an X application that has an Imakefile? ANSWER: Type xmkmf to generate the Makefile. Type make. QUESTION: gcc complains the X libraries are not found or links static. ANSWER: Check out the -nojump -static options of GCC ... read the GCC FAQ. You can tell gcc what directories to search with -L. XI.H BUGS: ~~~~~~~~~ Restoration of the text screen fails on some hardware. Cant compile Xaw programs without -static in versions x11v1.1 or older. There is a glitch with the Xaw shared libs ... I haven't seen this in a while anyway its fixed in newer releases. Color problems with Xega .... fixed in latest version on tsx-11. from chuck@coplex.com (Chuck Sites) It is possible to run X386 on a Paradise VGA Plus. The X386.0 doc file has a small misprint. The Chipset is not pvga. It's pvga1. Anyway, under the line in /usr/X386/lib/X11/Xconfig VGA256, add, `chipset "pvga1"`. You will need a 512k board. There seems to be a problem with 800x600 mode that causes pixels to be misplaced in the center 1/3 of the screen. 640x480 works fine. Anybody out there might have a fix for that? You may want to use X386mono with 800x600 instead. Fix for missing numlock control in xfree86-1.1. use xmodmap to change the mapping: clear mod1 add mod1 = Alt_L keysym Alt_R = Mode_switch add mod5 = Mode_switch David (Dawes) Sources for X11_FAQ: Steve Kotsopoulos, Peter Hawkins, John Morris, MM. Corsini, K. Balasubramanian. Direct comments, questions, complaints to krishna at: balasub@cis.ohio-state.edu XII. NETWORKING and LINUX ============================ *** This section should be maintained by Philip Copeland *** (p_copela@csd.uwe.ac.uk). This first version was built by myself *** (MM. Corsini) from the original material posted by Phil in c.o.l. *** I hope the information provided below are readable and useful. *** Last Update: 16 Nov 92 01:12:45 GMT **** In the ANSWER part the I/MY stands for P. Copeland **** QUESTION: Where can I find useful information about networking for Linux ? ANSWER: Join the NET channel on the multi-channel list. The FAQ/INTRODUCTION written by P. Copeland should be posted every 2 weeks. QUESTION: What do I need to get started ? ANSWER: To use TCP/IP on local ethernet you will need the following 1) A linux machine with linux kernel 0.98.4 or newer 2) A WD8003/WD8013 compatible MEMORY MAPPED ethernet card but WD8013 is probably the best to use due to its electronic reconfiguration rather than jumper settings although you'll probably need DOS to set it up You should note that the kernel will always claim to have found a WD8013. If this bothers you, change the printk in linux/net/tcp/we.c to reflect your hardware. *NOTE* no special hardward is needed to communicate with yourself Currently I know of three cards that will work (please tell me if there are more) support for the ne2000 is being worked on but little has been heard of it's progress These are the WD8013, WD8003, and the SMC Elite 16. 3) If you are only going to use 'loopback' mode, you probably won't need a card either! A special loopback device is used to comunicate with yourself 4) some tcp/ip software eg telnet/ftp/talk/finger/rcp/ rsh/various other stuff like daemons etc... 5) Know the IRQ's of your internal cards. 6) A lot of coffee and one of those stress relieving gadgets you can get in the local market. QUESTION: Where to start ? ANSWER: First off you'll need to rebuild the kernel with networking compiled into the linux kernel. You do this by removing the '#'s in linux/net/Makefile on lines 13,14 and 26 if they haven't already been removed. Next you'll need to calibrate your network card. Decide what IRQ setting you'll need for the network card. Anyway for those who are frexible, the standard kernel parameters for this are :- INT = 5 mem = D0000 i/o addr = 280 memory start = D0000 memory end = D2000 (8K block for 8003, make it D4000 16k for the wd8013 ) but these can be changed on lines 12-17 (16,17 being the most important) of the file linux/net/tcp/Space.c *NOTE* if you have problems with the memory start addr, please get in touch with bir7@EDU.Stanford.leland Future versions of the TCP/IP code will be setable at boot time via ioctl's. For those of you who do not have the wd8013 card, please refer to the ethernet board documentation on the jumper settings you may have to change. Right, compile the kernel (You may need to do a 'make clean dep Image') and hopefully on the next reboot with the new kernel it should detect your card telling you of the ethernet number it is, and also that a new family of sockets (AF_INET) are available. If your card is incorrectly inserted (I know you wouldn't) it could cause all kinds of errors to be reported. At this stage you have a kernel which supports tcp/ip via the ethernet board in your machine but knows nothing of networking, that is where the software in the tcpip suites becomes important as it is this software that understands networking protocols. QUESTION: What files do I need and setup info ? ANSWER: the 0.8.0/0.8.1 suites have reasonable enough documentation to get the various working parts out into somewhere useful on your system, typically /usr/etc/inet and /etc having followed the net install shell script you'll probably find that it asked some questions that you hadn't a clue about,... well ok lets look at it. Enter Ip Address for (your host) (aaa.bbb.ccc.ddd) here you are being asked what network address you would like to be known as. Ip address are unique numbers so as to identify you machine from another on a multiuser network. Ip numbers are typically of the 0-255.0-255.0-255.0-255 range so valid answers are 243.123.4.23 or 192.35.173.3 etc but 324.234.545.2 is completely wrong. Enter Net Address for (your hostname) (aaa.bbb.ccc.0) Here you are being asked for your subnetwork address. A quick way of getting the question right is to type in whatever you have for your ip address but make the last number 0 eg if my ip address was 135.56.33.155, my 'safe' Net address would be 135.56.33.0 0.0.0.0 means the whole world and is probably what slip people shoul use. Enter Router Address for (your hostname) (aaa.bbb.ccc.ddd) Routers tend to have 2 ethernet boards in them whith differing network numbers for them so that they can 'bridge' between different numbered networks, eg you could not talk directly to a ip address of 192.35.173.12 from an ip address of 192.35.175.15 but a machine in the middle with two ip address 192,35.173.4 and 192.35.175.3 can 'collect' the data from the xxx.xxx.173.xxx network and transfer it to the xxx.xxx.175.xxx network All we have to do here is stick in the ip address of the local router in this case it would be 192.35.173.4 (clear as mud I know but it's as good as it gets) If you don't have a router,... just stick in 0.0.0.0 meaning don't route anything. Enter Domain name for (your host) This isn't too bad, domain names are 'convenient' labels eg uwe.ac.uk is the domain name that appends to all the machines on site so that a sun called csd would be known as csd.uwe.ac.uk Name Server for Domain (aaa.bbb.ccc.ddd) If your networked to the local Uni/technical collage your in luck and it shoul be able to serve you with a name server service, find out from your local network controller what machine distributes the service. If you are unlucky enough NOT to have a nameserver, just stick in your own IP address, you'll just have to run your own nameserver. Ok time for a quick check of what you *SHOULD* have in /usr/etc/inet config - This sets up the ethernet ip tables inetd - Daemon process that invokes other network daemons inetd.conf - Configuration file for inetd about the other daemons install.net - The semi automatic script I just talked about named-xfer - Used for updating the nameserver records named.reload - used to load in the named named.restart - user to stop and restart the named process rc.net - a network rc file called from /etc/rc.local from /etc/rc! services - a file specifying what 'port' numbers certain services are available on telnetd - daemon for connecting reqesting external sites to your machine for interactive logins named - the nameservice daemon QUESTION: What is DNS ? ANSWER: DNS stands for Domain Name System. It doesn't rely on a single large table; it is a distributed database system that doesn't bog down as the database grows. DNS currently provides information on approximately 700,000 hosts. DNS also guarentees that the new host information will be disseminated to the rest of the network as it is needed. QUESTION: What are the configuration files for the DNS nameserver; and how can I fix them ? ANSWER: DNS configuration reqires that a number of files be edited in the case of Linux these files are minimally (resolv.conf can be optional) /usr/etc/inet/ resolv.conf or named.boot a_hosts_table (normally called named.hosts) named.boot: domain uwe.ac.uk primary uwe.ac.uk /usr/etc/inet/a_hosts_table resolve.conf: domain uwe.ac.uk nameserver 192.35.173.2 a_hosts_table: @ IN SOA slave.uwe.ac.uk. \ root.slave.uwe.ac.uk. ( 1.1 ;serial 3600 ;refresh every 10 hours 300 ;retry every 6 minutes 36000000;expire after 1000 hours 3600 ; default dtl is 100 hours ) IN NS slave.uwe.ac.uk. slave IN A 192.35.173.2 hal IN A 192.35.173.1 zen IN A 192.35.173.30 . . . mother IN A 192.35.173.69 For most people, a nameserver will be available in which case the only file really needed is resolv.conf which would contain only the domain name of the site and a nameserver ip address to point to all the named functions are thus the responsibility of the nameserver and not your machine (crafty huh?) Now unfortunately there are those of us that were just plain born unlucky and had to RTFM so,... where a nameserver is not available it is possible to run a nameserver service on your local machine. The following is a list of flies that you will eventually need although just named.boot and a_hosts_table will suffice named.boot: Sets general named parameters and points to the sources of the domain database information used by this server. The sources can be local disks or remote servers. named.ca: Points to the root domain servers named.local: Used to locally resolve the loopback address named.hosts: The zone info file that maps host names to IP addresses named.rev: the zone file for the reverse domain that maps IP addresses to host names (you'll prob never touch it so i'm going to skip it's description unless people get upset enough to lynch me) QUESTION: What is NFS ? ANSWER: NFS stands for Network Filing System. Network filing systems are convenient mechanisms which allow your machine access to more disk space that it actually has by 'borrowing' disk space from another networked machine for either sharing of common data or if allowed, the storing of data generated by your machine. NFS is still in alpha testing and has the unfortunate handicap of not being able to run binaries over the interface due to mmap support not being available at the moment but shell scripts can be run. NFS has several benifits, 1) it reduces local disk storage requirements because a network can store a single copy of a directory, while the directory continues to be fully axcessible to everyone on the network. 2) NFS simplifies central support tasks, becaue files can be updated centrally, yet be available throughout the network 3) NFS allows users to use familiar UNiX commands to manipulate files with rather than learning new ones. There is no need to use rcp/tftp/ftp to copy files, just 'cp' will do NFS is controlled by several files /etc/exports /usr/etc/inet/rc.net The /etc/exports file allows your machine to decide what local filesystems it will allow remote clients to NFS mount and decide what access those clients should have to your filespace. The /usr/etc/inet/rc.net file is used to start the named services and nfs QUESTION: What are the most common trouble with the Linux Networking ? ANSWER: One of the most common complaints requards the config command what isn't often noted is that this has to be recompiled from the 0.8.1 sources (available currently on tsx-11.mit.edu: as /pub/linux/ALPHA/tcpip/tcpip-0.8.1.tar.Z). Another problem that crops up is that some binaries that are distributed requires libc.2.2.2 to be present (mine I've no idea what version/wher it came from but it's 173060 bytes long if it helps!) Other people think that it's their version of libraries that cause the problem but can't find the source code for the various utils to recompile. Well sorry folks you are out of luck, the source code for those utils like ftpd and inetd are jealously held back because they are buggy and full of ugly hacks so rather than have the net flooded with complaints, they have been compiled into binary form and shoved out the door with innocent looks about them. Of note are inetd and named from the BSD sources, someone needs to port them as the current ones are erm.. well not really inetd/named. A new telnetd will probably be available after the kernel pty's are fixed which looks as though it'll break a lot of ioctl code. QUESTION: Any tricks that can help me to setup my system ? ANSWER:Several things that can help 1) upgrade your kernel to the latest one that you can grab a copy of (currently at time of writting 0.98.4) 2) join the NET mail channel, you can learn an awful lot from the guys on this channel (like the various new copyrighted techniques for tearing out your hair) 3) try and upgrade your C compiler and libraries to at least version 2.2.2d7 4) binary distributions of various network probrams can be found on sunsite.unc.edu,.. always read the README files they are there for a reason! (personal show/contacts/etc..) 5) Depending on your type of problem, contacting the author of the software or the person who ported the software would be a better choice. 6) Complain bitterly to me if I haven't covered your problem and I'll get it sorted for the next FAQ Cast of this section ==================== Ross Biro - Without whom all this wouldn't be possible and who pointed out holes in my documentation. Also contributed the history of tcp/ip on linux after he saw my rather perverted view of it. Mitch DSouza - Constant alpha tester. Also pointed out mistakes and made critical and helpfull suggestions (like getting a spell checker). Also gave me his Tel No. which I used to annoy him with. Rick Sladkey - The current Author of the NFS client server code who with the help of Doug Quale repatched the kernel to support networking filesystems. The pioneers - Mentioned in the history of TCP/IP 0.8.[01] by Ross earlier in this FAQ The supporting - You know who you are (probably, depending on how extras much virtual beer you had last night) for contributing to the network code. Linus Torvalds - The elusive ecentric UNiX kernel coder who probably burns more CPU time on compiling than anyone else Here's to a long and healthy kernel development program and a Nobel equiv award for his efforts. Philip Copland - The only sad person to take on the FAQ because I was getting annoyed at the number of 'petty' tcp/ip code problems being asked on the net. Besides of which I wanted to give something useful towards Linux which I've used since 0.10 (does this make me a vetrian?) XIII. EMACS for LINUX ===================== *** This section is maintained by Rick Sladkey (jrs@world.std.com) *** Last Update November 1992. XIII.A. GENERAL INFORMATION XIII.B. GNU EMACS for LINUX XIII.A. GENERAL INFORMATION ~~~~~~~~~~~~~~~~~~~~~~~~~~~ This is a short list of Frequently Asked Questions about GNU Emacs under Linux. It does not address general questions about Emacs which are not Linux specific. For general help about Emacs, 1) learn to use and read the online documentation, 2) read the real Emacs FAQ found in emacs/etc/FAQ, and 3) read the newsgroup gnu.emacs.help. Rick Sladkey <jrs@world.std.com> XIII.B. GNU EMACS for LINUX ~~~~~~~~~~~~~~~~~~~~~~~~~~~ QUESTION: Does Linux Emacs use the shared libraries? ANSWER: Yes. It wasn't easy. If you have any problems with them let me know. Also contact me if you would like static binaries. QUESTION: What version of the compiler was used? Which shared libaries? ANSWER: This describes version of GNU Emacs 18.59 for Linux 0.97 and above compiled with GCC 2.2.2d7 using the libc.so.4.1 and libX11.so.2.1 shared libraries. QUESTION: Which files do I need? ANSWER: emacs-18.59a.tar.Z this file, sample default.el and diffs for this version, the eight-bit patch, iso-latin-1.el and eight-bit.el emacs-etc-18.59a.tar.Z emacs support programs and misc info emacs-bin-18.59a.tar.Z shared emacs binary and its doc file x11emacs-bin-18.59a.tar.Z shared x11emacs binary and its doc file QUESTION: How do I install them? ANSWER: According to Linux convention, cd to /usr and untar the packages. QUESTION: Does Linux Emacs support eight-bit input/output? ANSWER: Yes. It is new with this version. It uses the so-called "ctl-arrow" patch. See the file README.8bit for more information. QUESTION: How much disk space is required? ANSWER: Anywhere from 1 to 15 Meg. Emacs works reasonably well with no support files at all. With a judicious selection from lisp/*.elc and etc/*, quite a lot can be done using only 2 Meg. If you want all of lisp/*.elc, info/*, and etc/* this will require 4 to 6 Meg. If you unpack the whole source you need 8 Meg. If you collect info files like rare coins and install a lot of big lisp packages then Emacs may need its own partition. :-) QUESTION: Why does Emacs crash under Linux 0.98 patchlevel 4 or higher? ANSWER: It crashes becuase of the a new 256-bit wide fd_set structure. Sometimes progress requires sacrifice. QUESTION: Why can't Emacs find its support files anymore? ANSWER: This is because older versions of Emacs were compiled with "/usr/local/emacs" based paths. The current version is compiled with "/usr/emacs" paths. If you have a previous installation, just "mv /usr/local/emacs /usr" and you're done. If you can't bear to part with the "/usr/local" pathnames because of inertia then do "ln -s /usr/local/emacs /usr" and you can have them both. QUESTION: How do I get Emacs to recognize my cursor keys? ANSWER: Simple. Don't use them. :-) Seriously, there are as many ways to do this are there are elisp hackers but the preferred way is to follow the pattern set by the other terminal definition files in emacs/lisp/term/*.el. For just arrow keys you can just copy vt220.el to console.el and that's it. For function keys and the others see the sample default.el included with this file. QUESTION: What packages are particularly useful under Linux? ANSWER: Because info format is the documentation standard of the GNU project and just about everything except the kernel comes from FSF, you will find that Dave Gillespie's enhanced info package is very useful. It allows multiple info directories, space bar paging, and supports compressed info files. Please learn to use info. Imagine Unix life without man. Others that I highly recommend are Sebastian Kremer's enhanced dired directory editor, Dave Gillespie's calc calculator, Masanobu UMEDA's gnus for usenet news, and Kyle Jone's vm for mail. All can be found in the OSU Emacs archive. See the real FAQ for more details. QUESTION: Does Linux Emacs use the shared libraries? ANSWER: Yes. It is very delicate. Emacs uses its own malloc and the library uses the standard one. Everything works as long as the two never meet. QUESTION: Does Linux Emacs support the X Window System? ANSWER: Yes. However, there are two binaries. One without X support (about 485k) and one with X support (about 515k). QUESTION: Do I need both Emacs if I don't always use X? ANSWER: No. The X11 version works equally well inside or outside of X. If you get the message "Check your DISPLAY variable" it means that you have defined DISPLAY in your ~/.profile (or whatever). You can fix this by starting Emacs with 'emacs -nw' or by removing the DISPLAY variable from your ~/.profile and putting it in you ~/.xinitrc. QUESTION: Why doesn't Emacs use the settings in my .Xdefaults/.Xresources file? ANSWER: You are probably using the word "emacs" and your X version of emacs is called x11emacs. Either use the word "Emacs" in your resource file or rename x11emacs to emacs. See above question on why this is reasonable. QUESTION: I read about some menu that is supposed to pop up when I press some mouse button. Does this work with Linux Emacs? ANSWER: Yes. This requires XMenu support to be compiled in. Former versions did not support it because it did not work correctly. QUESTION: Sometimes Emacs crashes with a SIGALRM message. What's wrong? ANSWER: You need to upgrade to a newer version of bash. Some older versions of bash were compiled with buggy libraries that caused bash to send a SIGALRM to its parent in some circumstances. Recent versions do not exhibit this problem. QUESTION: Why does Emacs always put me in the root directory?